<text><span class="style7">rant Foundations:</span><span class="style1">National Endowment for the Arts1100 Pennsylvania Avenue, N.W.Washington, D.C 20506(202) 682-5532National Endowment for the Humanities1100 Pennsylvania Avenue, N.W.Washington, D.C 20506(202) 786-0438</span></text>
</content>
<content>
<layer>card</layer>
<id>3</id>
<text><span class="style7">rant Writing and Fundraising Support:</span><span class="style1">The Foundation Center79 - 5th AvenueNew York, NY 10003-3050(800) 424-9836*(call for regional branch office locations)</span></text>
</content>
<name>Resources</name>
<script></script>
</card>
card_6596.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This is the resume section. Include a resume for the major personnel in the project (i.e. for motion picture projects, include "above the line" personnel such as the director, producer, and writer).If you have press coverage about yourself, or letters of reference, etc., this is the place for them. Do not go overboard. Only include the items that are relevant to what you are trying to accomplish with your project. (i.e. do not include photos of your bowling trophy if you are writing a book about "Building Solar Houses"!)</text>
</content>
<name>Credentials</name>
<script></script>
</card>
card_6163.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The budget should be in two parts. First, the budget summary - a concise (hopefully one-page) budget for your project. It should be divided into supplies, services, labor and in-kind donations. (In-kind donations are supplies, services and/or labor that are donated by you or your organization, or are being donated by other people or organizations).The second part should be a line-by-line justification of the reasons you need what you are asking for. Be truthful and honest in this section. If you just personally want a "Mondo-500XYZ", and there is no reason you need one for your project, that will come across to your potential grant funders. Only ask for what you need - grants aren't gifts, they are resources for working.</text>
</content>
<name>Budget</name>
<script></script>
</card>
card_5913.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>A timeline is more or less a promise of what you are going to do and when you are going to do it. It is important for two reasons: 1) it shows your potential funders that you have thought of every step needed to complete your goal(s), and 2) it shows that you have properly allocated enough time to successfully complete each phase of the project.For instance, if you are writing a reference book, and you only allow two weeks for research, your potential funding institution is going to assume that you have not allowed enough time to do a good job and therefore the end product will not be of use to anyone, and therefore they should not fund it. Get the point?</text>
</content>
<name>Timeline</name>
<script></script>
</card>
card_5678.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>...or "Dissemination". This area talks about how you are going to get what you have done out into the public. If it is a film, book, music recording, etc. you will obviously distribute your project. If it is a theater piece, performance, etc, you will obviously advertise shows for your project. If it is research for a university degree, you will turn that research over to your professors or university.Whatever the case may be, you need to explain how you are going to get what you have done into the hands of someone (or many people) who can see, use, appreciate and/or evaluate it. Funders do not want to fund something that is going to sit on someone's closet shelf once it is finished. They want to know that you have given serious consideration to how you are going to disseminate your project. Without this section, your project's credibility will be seriously hindered.</text>
</content>
<name>Distribution</name>
<script></script>
</card>
card_5480.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This area should go into full detail of your project. Do not leave any details that are important out. On the other hand, do not explain things that are self-evident or common sense. If there is a gap in the process of your project, or an item that does not make sense, your potential funders will have questions as to whether you have really sat down and done your homework by planning everything out. This is not good. Be specific and detailed.Be sure and point out the goals of your project. List them in a clear, concise format. Do not make your goals redundant. Be ruthlessly clean, sharp and concise!The last part of this section should address how you will evaluate if you have met your goals or not. (For instance, if you are producing a theater piece, an obvious evaluation would be ticket sales. Another would be critic's reviews.) Be sure you address the evaluation part of your description as it will show that you have made plans to evaluate and continue your project if possible and applicable. </text>
</content>
<name>Description</name>
<script></script>
</card>
card_4672.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Why you? Why not my brother-in-law? What's so special about what you're doing, and how you're doing it, that 'they' should give you lots-o-money???This is the area to toot you own horn - and very loudly! Remember, no one else is going to toot your horn for you (if they do, include it here), so go for it! This, unfortunately, is the area where you have to "sell yourself". We would all love to do what we want, when we want, without ever having to ask permission, approval or for the money to do it, but alas, this is the reason your are writing this grant, isn't it?Make a real effort to get the people who are reading your application excited about it. Point out all the good strong points. Use 'action' words which suggest a positive attitude (i.e. say 'accomplish' instead of 'execute' a task).If you have any press clippings, reviews, etc. you want to include, make reference to them here, and include them in your appendices. DO NOT INCLUDE samples, demos, videotapes, or any non-written material here unless specifically asked for. 99% of the time, unsolicited samples confuse the selection process and actually may hurt your application more than help it.</text>
</content>
<name>Why You?</name>
<script></script>
</card>
card_4490.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The background of your grant application should state the events leading up to your current project. This is not your credential or resume area, but more a perspective of what else is or was available in the same field as your project, who is doing or has done it, why theirs is or was good or bad, and how yours will be better.You should be very specific and knowledgeable in this area, so that your funders know that you are willing to acknowledge the "competition" and learn from, and correct their mistakes, as well as possibly work with them, so that you are not duplicating existing efforts. Be very honest in this area, you'd be surprised how many people know what is really going on.You should make sure and point out how your project fits into the scene of what is already available. Are you filling an unfilled gap? Doing a better job that what is available? Addressing a need that no one else does? Make sure and point these factors out.If you have done your homework on your potential funding organization (like you should), try and address the specific funding goals and criteria that the organization might have in this section.</text>
</content>
<name>Background</name>
<script></script>
</card>
card_4214.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The introduction of your grant should be fairly short. Basically, someone is going to read you summary sentence and hopefully say "Wow, this sounds great!". They will then read the introduction to make sure it really is great, and then pass it on to a specialist to examine in detail, (once it has passed the preliminary guideline qualifications and other criteria).I sometimes take all the sentences I deleted to get my one sentence summary and re-use those here as a one or two paragraph introduction. Anything more than just a basic overview of the application should be saved for the detailed description area, where you may go into detail until your heart's desire (or you reach the maximum page limit, whichever comes first!).</text>
</content>
<name>Introduction</name>
<script></script>
</card>
card_3734.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The opening of your grant application should be a one sentence summary of your entire project. Some foundations may require you to use so many words or less, or to use only a specified section of a form, limiting the number of words you may use in the sentence.I find it best simply to write a sentence that feels like a comfortable length (i.e. no sentences in legal jargon!). The summary sentence is the most important part of your application, as it is often used to summarize your grant in the review process. If it doesn't sound good, your entire grant may never be read!Writing a one sentence summary of your project also forces you to determine precisely what it is you are trying to do. It is a good exercise in clarity and in focusing your project's theme.</text>
</content>
<name>Sentence</name>
<script></script>
</card>
card_3030.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
 (January 1993).iso/Files/Hyper/G/GRANT WRITER 2.0.cpt/GRANT WRITER 2.0/BMAP_3984.png){kind=link}
 (January 1993).iso/Files/Hyper/G/GRANT WRITER 2.0.cpt/GRANT WRITER 2.0/PATs.png){kind=link}